Description

When opening the Perps order view, the component syncs the transaction "pay token" from pending config (e.g. last selected payment token). The previous logic re-ran this sync on every effect run, so if the user changed the token in the "Pay With" modal, a later effect could overwrite their choice with the pending token again.

Changes:

• Pending config is now applied once per load (or when initialAsset changes). A ref tracks which pending token was already applied so we don’t overwrite the user’s in-session token selection.
• When initialAsset changes (e.g. user switches from BTC to ETH), the "applied" state is reset so pending config is re-applied for the new asset.
• When pending config has no selected token, setSelectedPaymentToken(null) is only called once, not on every effect run.

This keeps the intended "restore from pending config" behavior on first load and on asset change, without undoing the user’s token choice when they’ve already changed it in the same session.

Changelog

CHANGELOG entry: Fixed Perps order view reverting the user’s payment token selection to the pending config after they had changed it in the Pay With modal.

Related issues

Jira issue: https://consensyssoftware.atlassian.net/browse/TAT-2572
Fixes: #26118

Manual testing steps

Feature: Perps order view pay token and pending config
  Scenario: user changes payment token and it is not overwritten by pending config
    Given user is on Perps order view with a pending payment token (e.g. USDC)
    And pay token is initially synced from pending config
    When user opens Pay With modal and selects a different token (e.g. DAI)
    Then the selected token remains DAI and is not reverted to the pending token (USDC)

  Scenario: pending config is re-applied when switching asset
    Given user is on Perps order view for asset BTC with pending token A
    And pay token was synced to token A
    When user switches to asset ETH (e.g. different market) and pending config has token B for ETH
    Then pay token is synced to token B for the new asset

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.